Fix StringDType not roundtripping through Zarr v3 - #11474
Open
stanbot8 wants to merge 2 commits into
Open
Conversation
|
Thank you for opening this pull request! It may take us a few days to respond here, so thank you for being patient. |
github-actions
Bot
added
topic-backends
topic-zarr
stanbot8
force-pushed
the
fix/11466-stringdtype-zarr
branch
2 times, most recently
from
July 27, 2026 06:28
db97531 to
0a42250
Compare
stanbot8
force-pushed
the
fix/11466-stringdtype-zarr
branch
from
July 28, 2026 19:08
0a42250 to
62c3064
Compare
stanbot8
changed the title
stanbot8
changed the title
stanbot8
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Storage loses native NumPy StringDType metadata.
Preserve NumPy StringDType for variables, coordinates, and scalars in Zarr format 3 round trips.
Keep the existing UTF-8 encoding when a StringDType carries an
na_object, because zarr rejects such adtypenatively. A test pins the routing.Closes #11466.